Extending signal coverage and charge duration of a user equipment

ABSTRACT

A device may receive signal information associated with a wireless signal or charge information associated with a charge level. The signal information may indicate a signal strength of the wireless signal. The charge information may indicate the charge level of a battery of the device. The device may determine whether the signal strength or the charge level satisfies a threshold. The device may configure a parameter or a setting of the device to cause the device to operate according to a long term evolution (LTE) category based on determining whether the signal strength or the charge level satisfies the threshold. The LTE category may be different from a default LTE category of the device and may define an uplink/downlink capability specification. The device may attach to a network in association with configuring the parameter or the setting to cause the device to operate according to the LTE category.

BACKGROUND

A wireless device may operate by communicating via radio waves using asystem of base stations. The base stations may send and receive calls,and relay the calls to other base stations. The coverage of a basestation may include the geographic area where the base station cancommunicate with the wireless device. In addition, a wireless device mayoperate using batteries as a power and/or energy source. The state ofcharge of the wireless device battery may include the amount of powerand/or energy left in the battery compared with the amount power and/orenergy the battery had when the battery was full.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for extending signalcoverage and charge duration of a user equipment;

FIG. 5 is a flow chart of an example process relating to the exampleprocess shown in FIG. 4;

FIG. 6 is a flow chart of an example process relating to the exampleprocess shown in FIG. 4;

FIG. 7 is a call flow diagram of an example implementation relating tothe example process shown in FIG. 4; and

FIG. 8 is a call flow diagram of an example implementation relating tothe example process shown in FIG. 4.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

User equipment (UE), such as smartphones, mobile phones, or tabletcomputers, may need a sufficient signal strength to communicate and/or asufficient charge level to operate. However, a UE may be located in anarea without sufficient signal strength to communicate, such as in arural area, within a structure (e.g., a building, a tunnel, etc.), orthe like. In addition, particular functions of the UE (e.g., streamingvideo, receiving and transmitting background data, web browsing, etc.)may discharge the battery of the UE at a rate faster than desirable,such as when the battery has a low charge level.

Implementations described herein may enable a UE to configure to operateaccording to a particular UE category or device category (e.g., a thirdgeneration partnership project (3GPP) UE category) based on a signalstrength of a wireless signal received by the UE and/or a charge levelof a battery of the UE satisfying a threshold. In this way,communications of the UE may be improved by permitting the UE tocommunicate when the signal strength would otherwise prevent, ordisrupt, the UE from communicating. Additionally, or alternatively,battery and/or power resources of the UE may be conserved by modifyingone or more particular functionalities of the UE that consumesignificant battery and/or power resources.

FIGS. 1A and 1B are diagrams of an overview of an example implementation100 described herein. Example implementation 100 includes a provisioningdevice, a base station, and a house. For this example, assume the houseincludes a basement having a UE located therein. Assume further that theUE has a battery charge level of three percent (3%).

As shown by FIG. 1A, and by reference number 110, the base station maytransmit a wireless signal. For example, the base station may transmit aradio frequency (RF) signal. As shown by reference number 120, thewireless signal from the base station may experience interference, dueto, for example, a portion of the structure of the house and/or basement(e.g., a wall, a roof, or a foundation). In some cases, the wirelesssignal may experience interference other than physical interference,such as radio interference. In addition, the wireless signal received bythe user equipment may be weakened due the user equipment being locatedgeographically distance from the base station.

As shown by reference number 130, the UE may determine that the signalstrength of the wireless signal received by the UE and/or the batterycharge level of the UE do not satisfy a threshold. For example, the UEmay determine that the signal strength of the wireless signal does notsatisfy a threshold quantity of decibels to milliwatts (dBm). As anotherexample, the UE may determine that the charge level of the battery doesnot satisfy a threshold amount of voltage.

As shown by FIG. 1B, and by reference number 140, the UE may configureto operate according to long term evolution (LTE) category M1 and maytransmit an LTE category M1 attach request message to the base station.For example, the UE may configure settings or parameters related tofunctionality of the UE to operate according to LTE category M1 based onthe signal strength and/or the battery charge level not satisfying athreshold. In some implementations, configuring to operate according toLTE category M1 may improve communication and/or extend a charge of abattery of the UE, as described elsewhere herein. As further shown inFIG. 1B, the UE may transmit the LTE category M1 attach request messageto the provisioning device via a base station.

As shown by reference number 150, the provisioning device may determinethat the UE is permitted to operate according to LTE category M1. Forexample, the provisioning device may use a data structure to identifyinformation indicating that the UE is permitted to operate according toLTE category M1.

As shown by reference number 160, the provisioning device may transmitan LTE category M1 attach accept message to the base station, and thebase station may transmit the LTE category M1 attach accept message tothe UE. Based on receiving the LTE category M1 attach accept message,and as shown by reference number 170, the UE may operate according toLTE category M1.

In this way, communications of the UE may be improved by permitting theUE to communicate when the signal strength would otherwise prevent theUE from communicating. Additionally, or alternatively, battery and/orpower resources of the UE may be conserved by modifying one or moreparticular functionalities of the UE that consume significant batteryand/or power resources.

As indicated above, FIGS. 1A and 1B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 1A and 1B. For example, rather than configuringspecifically to LTE category M1, the UE may configure to any LTEcategory that is a lower category than the LTE category at which the UEis currently operating. In addition, the UE may configure to anothertype of device category, such as a non-LTE category (e.g., a wirelessdevice category other than an LTE category). For example, the UE mayconfigure to device category narrow band 1 (NB1) (also referred to ascategory narrow band-Internet of things (NB-IoT)), rather thanconfiguring to LTE category M1. In other words, while implementationsare described herein with respect to LTE categories, and specificallyLTE category M1, implementations may include any type of LTE or non-LTEdevice category.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include user equipment (UE) 210, a base station220, a mobility management entity device (MME) 230, a provisioningdevice 240, and a network 250. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 210 includes one or more devices capable of communicating with basestation 220 and/or a network (e.g., network 250). For example, UE 210may include a communication and/or computing device, such as a mobilephone (e.g., a smart phone or a radiotelephone), a laptop computer, atablet computer, a gaming device, a wearable communication device (e.g.,a smart wristwatch, a pair of smart eyeglasses, or an activity band), ora similar type of device. In some implementations, UE 210 may detect asignal strength of a wireless signal and/or a charge level of a battery,as described elsewhere herein. Additionally, or alternatively, UE 210may configure to operate according to a particular UE category based onthe signal strength and/or the charge level, as described elsewhereherein.

Base station 220 includes one or more devices capable of transferringtraffic, such as audio, video, text, and/or other traffic, destined forand/or received from UE 210. In some implementations, base station 220may include an evolved Node B (eNB) associated with a long termevolution (LTE) network that receives traffic from and/or sends trafficto an external network via a serving gateway (SGW) and/or a packet datanetwork gateway (PGW). Base station 220 may send traffic to and/orreceive traffic from UE 210 via an air interface. In someimplementations, base station 220 may include a small cell base station,such as a base station of a microcell, a picocell, and/or a femtocell.

MME 230 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with UE 210. In someimplementations, MME 230 may perform operations relating toauthentication of UE 210. Additionally, or alternatively, MME 230 mayfacilitate the selection of a particular serving gateway (SGW) and/or aparticular packet data network gateway (PGW) to serve traffic to and/orfrom UE 210. MME 230 may perform operations associated with handing offUE 210 from a first base station 220 to a second base station 220 whenUE 210 is transitioning from a first cell associated with the first basestation 220 to a second cell associated with the second base station220. Additionally, or alternatively, MME 230 may select another MME (notpictured), to which UE 210 should be handed off (e.g., when UE 210 movesout of range of MME 230).

Provisioning device 240 includes one or more devices, such as one ormore server devices, capable of managing (e.g., receiving, generating,storing, processing, and/or providing) information associated with UE210. For example, provisioning device 240 may manage subscriptioninformation associated with UE 210, such as information that identifiesone or more UE categories according to which UE 210 is permitted tooperate, information that identifies a subscriber profile of a userassociated with UE 210, information that identifies services and/orapplications that are accessible to UE 210, location informationassociated with UE 210, a network identifier (e.g., a network address)that identifies UE 210, information that identifies a treatment of UE210 (e.g., quality of service information, a quantity of minutes allowedper time period, a quantity of data consumption allowed per time period,etc.), and/or similar information. Provisioning device 240 may providethis information to one or more other devices of environment 200 tosupport the operations performed by those devices.

In some implementations, provisioning device 240 may include a homesubscriber server (HSS), a policy and charging rules function (PCRF), ora similar type of device. Additionally, or alternatively, provisioningdevice 240 may include an open mobile alliance device management (OMADM)device, or a similar type of device, capable of providing information,such as service information, related to whether UE 210 has permission toconfigure to operate according a particular UE category. For example, UE210 may provide the information to enable UE 210 to determine whether UE210 has permission to operate according to the particular UE category,thereby reducing or eliminating the need for provisioning device 240 todetermine whether UE 210 has permission.

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., an LTEnetwork, a 3G network, or a code division multiple access (CDMA)network), a public land mobile network (PLMN), a local area network(LAN), a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the Public Switched Telephone Network (PSTN)),a private network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, a cloud computing network, or the like, and/or acombination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to UE 210, base station 220, MME 230, and provisioningdevice 240. In some implementations, UE 210, base station 220, MME 230,and provisioning device 240 may include one or more devices 300 and/orone or more components of device 300. As shown in FIG. 3, device 300 mayinclude a bus 310, a processor 320, a memory 330, a storage component340, an input component 350, an output component 360, and acommunication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a processor (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), and/or an accelerated processing unit (APU)), amicroprocessor, and/or any processing component (e.g., afield-programmable gate array (FPGA) and/or an application-specificintegrated circuit (ASIC)) that interprets and/or executes instructions.In some implementations, processor 320 includes one or more processorscapable of being programmed to perform a function. Memory 330 includes arandom access memory (RAM), a read only memory (ROM), and/or anothertype of dynamic or static storage device (e.g., a flash memory, amagnetic memory, and/or an optical memory) that stores informationand/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for extending signalcoverage and charge duration of a UE. In some implementations, one ormore process blocks of FIG. 4 may be performed by UE 210. In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including UE210, such as base station 220, MME 230, and provisioning device 240.

As shown in FIG. 4, process 400 may include receiving signal informationthat indicates a signal strength of a wireless signal received by a UEand/or charge information that indicates a charge level of a battery ofthe UE (block 410). For example, UE 210 may determine a signal strengthof a wireless signal received by UE 210 and/or a charge level of abattery of UE 210 (e.g., by measuring the signal strength or the chargelevel).

In some implementations, the signal strength of the wireless signal mayrelate to transmitter (e.g., base station 220) power output as receivedby UE 210 (e.g., expressed as decibels to milliwatts (dBm)). In someimplementations, the wireless signal may include an electromagneticsignal, such as a radio frequency (RF) signal, a Wi-Fi signal, aBluetooth signal, and/or the like. In some implementations, a chargelevel may relate to a capacity of a battery of UE 210 expressed as apercentage of maximum capacity. For example, the charge level mayinclude an expression of the present capacity of a battery as apercentage of maxim capacity. As another example, the charge level mayinclude an expression of a percentage of a maximum capacity of a batterythat has been discharged. In some implementations, a battery may includean electrochemical cell with connections to provide power to electricaldevices.

In some implementations, UE 210 may receive the signal informationand/or the charge information based on monitoring the signal strengthand/or monitoring the charge level. For example, UE 210 may monitor thesignal strength and/or charge level of UE 210 continuously,periodically, according to a schedule, or the like, such as by measuringthe dBms of the signal and/or measuring capacity of a battery of UE 210.

As further shown in FIG. 4, process 400 may include determining whetherthe signal strength and/or the charge level satisfy a threshold (block420). For example, UE 210 may determine whether the dBms of a signaland/or the charge level of a battery satisfy a threshold. In someimplementations, UE 210 may determine whether the signal strength and/orthe charge level satisfy a threshold based on monitoring the signalstrength and/or the charge level and comparing signal information to athreshold strength and/or charge information to threshold charge level.

In some implementations, a threshold may be configured by a user of UE210 and/or a network operator. In some implementations, a threshold,such as a threshold signal strength, may be configured on a per-callbasis, by type of call, or on per-contact basis. For example, a firstthreshold may be configured for calls to an emergency line or anemergency contact and a second threshold may be configured for calls toother parties. As another example, a first threshold signal strength,such as a signal strength associated with a particular quality ofservice, may be configured for calls to/from a first telephone numberand a second threshold signal strength associated with a differentquality of service may be configured for calls to/from a secondtelephone number. In some implementations, a threshold may include adefault threshold, a user-defined threshold, and/or the like.

In some implementations, UE 210 may determine whether the signalstrength and/or the charge level of UE 210 satisfy the threshold basedon comparing the signal information and/or the charge information and athreshold. For example, UE 210 may compare the signal information toinformation identifying a threshold signal strength. In someimplementations, the threshold signal strength may include a defaultthreshold, a threshold configured by network operator, a thresholdconfigured by a user of UE 210, or the like. Additionally, oralternatively, UE 210 may compare the charge information to informationidentifying a threshold charge level. In some implementations, thethreshold charge level may include a default threshold, a thresholdconfigured by network operator, a threshold configured by a user of UE210, or the like.

In some implementations, UE 210 may determine whether a particular typeof signal coverage is available. For example, UE 210 may determinewhether LTE signal coverage or roaming signal coverage is available(e.g., when UE 210 is outside of the coverage of network 250). In someimplementations, UE 210 may determine whether the particular type ofsignal coverage is available, rather than determining a signal strengthof a wireless signal and/or a charge level of a battery.

In some implementations, UE 210 may provide a notification or messagefor display to a user of UE 210 based on determining whether the signalstrength and/or charge level satisfy a threshold. For example, UE 210may provide the notification or the message when UE 210 determines thatthe signal strength and/or the charge level do not satisfy thethreshold. In some implementations, when providing the notification ormessage for display, UE 210 may permit the user to indicate whether theuser wishes to configure a parameter or a setting of UE 210.

As further shown in FIG. 4, process 400 may include configuring aparameter and/or a setting of the UE to cause the UE to operateaccording to a particular UE category (block 430). For example, UE 210may configure a parameter and/or a setting of UE 210 to cause UE 210 tooperate according to a particular UE category based on determiningwhether the signal strength and/or the charge level satisfy a threshold.

In some implementations, a parameter may include one or more 3GPP RFparameters (e.g., maximum UE channel bandwidth, uplink/downlink sharedchannel (UL/DL-SCH) transport block bits transmitted within atransmission time interval (TTI), or the like). Additionally, oralternatively, a parameter may include filter parameters, power outputparameters, or the like. In some implementations, a setting may includehardware settings of UE 210, such as a mode of a modem of UE 210,hardware settings related to communications and/or data transmissions ofUE 210, and/or the like. Additionally, or alternatively, a setting mayinclude a setting of an application installed on UE 210, executing on UE210, or executing remotely from UE 210. For example, a setting mayrelate to delay sensitivity of a voice client of UE 210, transmissionvoice buffer of UE 210, jitter buffer of UE 210, error tolerance of UE210, communications and/or data transmissions of UE 210, and/or thelike.

In some implementations, a setting, or a parameter, may relate to dataused by UE 210. For example, the setting or the parameter may relate todata used for a voice transmission, a short message service (SMS)transmission, a multimedia messaging service (MMS) transmission, abackground data transmission, or the like. As another example, whenconfiguring a setting or a parameter related to data used by UE 210, UE210 may configure UE 210 to repeat transmissions, such as when a signalstrength fails to satisfy a threshold. As another example, whenconfiguring a setting or a parameter related to data used by UE 210, UE210 may configure UE 210 to reduce transmissions, such as when a chargelevel of a battery of UE 210 does not satisfy a threshold.

In some implementations, a UE category may include an LTE category thatdefines a 3GPP combined uplink/downlink (UL/DL) capability specification(e.g., LTE category M1, LTE category 1, LTE category 2, etc.). Forexample, the 3GPP combined UL/DL capability specification may include adownlink shared channel (DL-SCH) specification, an uplink shared channel(UL-SCH) specification, and/or a transmission time interval (TTI)specification. In some cases, UE 210 may be described by a particular UEcategory according to which UE 210 may operate. For example, aparticular type of UE 210 that can operate according to LTE category 4may be described, or referred to, as an LTE category 4 device. In someimplementations, a UE category may include a device category associatedwith a type of device different than a UE. For example, a UE categorymay include a device category associated with an Internet of things(IoT), or machine-to-machine (M2M), device, such as an LTE machine typecommunication (LTE-M) category (e.g., LTE category M1, LTE category M2,etc.).

In some implementations, UE 210 may configure the parameter and/orsetting of UE 210 to cause UE 210 to operate according to a particularUE category. For example, UE 210 may configure the parameter and/or thesetting of UE 210 to cause UE 210 to operate according to LTE categoryM1. Additionally, or alternatively, UE 210 may configure the parameterand/or setting of UE 210 to operate according to a lower UE category(e.g., relative to the current UE category according to which UE 210 isoperating). For example, UE 210 may be configured to operate accordingto LTE category 4 (e.g. by default) and may configure the parameterand/or setting to operate according to LTE category 3, 2, M1, or thelike.

In some implementations, UE 210 may disable or reduce one of morefunctionalities of UE 210, such as when configuring to operate accordinga particular UE category. For example, UE 210 may disable or reducebackground data transmissions, streaming data, all data transmissionsother than voice and SMS data transmission, and/or the like.

In some implementations, when configuring to operate according to aparticular category, UE 210 may configure to operate according to a UEcategory associated with a different type of device. For example, asmart phone associated with LTE category 4 (e.g., an LTE UE-category)may configure to operate according to LTE category M1 (e.g., an LTEmachine type communication (LTE-M) category), typically associated withan Internet of things (IoT), or machine-to-machine (M2M), device, suchas a smart thermostat, a smart light switch, or a smart door lock. Thisenables UE 210 to benefit from configurations of settings and/orparameters associated with different types of devices.

As further shown in FIG. 4, process 400 may include attaching to anetwork based on configuring to operate according to the particular UEcategory (block 440). For example, UE 210 may find and select network250 while operating according to the particular UE category, such as LTEcategory M1. In some implementations, UE 210 may send an attach requestmessage to network 250 in association with attaching to network 250.

In some implementations, UE 210 may provide information to provisioningdevice 240 that identifies the particular UE category. For example, UE210 may provide the information to provisioning device 240 to enableprovisioning device 240 to validate whether UE 210 has permission tooperate according to the particular UE category.

In some implementations, when attaching to network 250, UE 210 maynegotiate settings with network 250 (e.g., by negotiating with a deviceconnected to network 250). In some implementations, when negotiatingsettings with network 250, UE 210 may negotiate settings for a powersaving mode (e.g., sleep time/duration settings). For example, UE 210may negotiate LTE power saving mode settings, such as a time of day, aday of the week, and/or an amount of time that UE 210 will be dormant.Additionally, or alternatively, UE 210 may negotiate transmission and/orreception settings. For example, UE 210 may negotiate LTE extendeddiscontinuous reception (eDRX) settings, such as idle time betweenpaging cycles, duration of a paging cycle, and/or the like. In this way,UE 210 may negotiate a setting of UE 210 that enables UE 210 to improvecommunications and/or charge duration of UE 210.

As further shown in FIG. 4, process 400 may include monitoring thesignal strength of the wireless signal and/or the charge level of thebattery (block 450). For example, UE 210 may monitor the signalstrength, or signal power, of the wireless signal received by UE 210and/or the charge level of the battery of UE 210. In someimplementations, when monitoring for signal strength, UE 210 may monitorfor a particular type of coverage. For example, UE 210 may monitor foravailability of roaming coverage.

In some implementations, UE 210 may prioritize switching to using aparticular type of coverage (e.g., roaming coverage) when available(e.g., rather than continuing to operate according to the particular UEcategory). Conversely, when monitoring for signal strength, UE 210 mayprioritize continuing to operate according to the particular UE category(e.g., rather than using a particular type of coverage when available).In some implementations, prioritization of using a particular type ofcoverage or operating according to a particular UE category may be basedon default settings, user selected settings, and/or the like.

In some implementations, when monitoring for charge level, UE 210 maymonitor for charging and/or connection to a power. For example, UE 210may monitor for connection to a wall charger, receipt of electricalcurrent from a power source other than the battery of UE 210, and/or thelike. In some implementations, UE 210 may monitor for charging and/orconnection to a power source to determine whether to continue to operateaccording to the particular UE category.

As further shown in FIG. 4, process 400 may include determining whetherthe signal strength and/or the charge level satisfy the threshold (block460). For example, UE 210 may determine whether the signal strengthsatisfies a threshold signal strength and/or whether the charge level ofa battery of UE 210 satisfies a threshold charge level. In someimplementations, determining whether the signal strength and/or chargelevel satisfy a threshold may be performed as described with respect toblock 420. For example, UE 210 may determine whether the signal strengthand/or charge level for UE 210 satisfy the threshold based on comparingthe signal strength information to a threshold signal strength and/orcomparing the charge information to a threshold charge level.

In some implementations, UE 210 may determine whether a particular typeof coverage (e.g., roaming coverage) is available. For example, UE 210may determine whether a particular type of coverage is available when,or rather than, determining whether the signal strength satisfies athreshold signal strength. Additionally, or alternatively, UE 210 maydetermine whether UE 210 is connected to a charger or a power sourceother than the battery of UE 210. For example, UE 210 may determinewhether UE 210 is connected to a charger or another power source when,or rather than, determining whether the charge level satisfies thethreshold charge level.

As further shown in FIG. 4, process 400 may include reconfiguring theparameter and/or the setting to cause the UE to operate according to adifferent UE category (block 470). For example, UE 210 may reconfigurethe parameter and/or setting to cause UE 210 to operate according to adifferent UE category, such as a lower UE category, or a higher UEcategory, than the UE category according to which UE 210 is currentlyoperating.

In some implementations, UE 210 may reconfigure the parameter and/or thesetting based on determining whether the signal strength and/or thecharge level satisfy the threshold. For example, UE 210 may reconfigurethe parameter and/or the setting based on the signal strength and/or thecharge level satisfying the threshold. Conversely, and as anotherexample, UE 210 may not reconfigure the parameter and/or the settingbased on the signal strength and/or the charge level failing to satisfythe threshold.

In some implementations, reconfiguration of the parameter and/or settingmay be performed as described with respect to block 420. For example, UE210 may reconfigure a 3GPP RF parameter, an UL/DL parameter, a filterparameter, a power output parameter, a hardware setting of UE 210,and/or a setting of applications of UE 210.

In some implementations, UE 210 may reconfigure UE 210 to operateaccording to a particular UE category. For example, UE 210 mayreconfigure UE 210 to operate according to a default UE category. Asanother example, UE 210 may reconfigure UE 210 to operate according to ahigher UE category than the UE category at which UE 210 is currentlyoperating, such by reconfiguring from operating according to LTEcategory M1 to operating according to LTE category 4.

In some implementations, UE 210 may detach from network 250 and reattachto network 250 based on reconfiguring. For example, UE 210 may detachand reattach to network 250 to enable provisioning device 240 tovalidate that UE 210 has permission to operate according to a differentconfiguration, a different UE category, and/or the like.

In some implementations, process 400 may include returning to block 450after block 470. For example, UE 210 may return to monitoring the signalstrength and/or the charge level, determining whether the signalstrength and/or the charge level satisfy a threshold, and reconfiguringthe parameter and/or the setting. In some implementations, process 400may include repeatedly performing blocks 450 through 470.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 relating to the exampleprocess shown in FIG. 4. Specifically, FIG. 5 shows an example processfor extending signal coverage of UE 210. In some implementations, one ormore process blocks of FIG. 5 may be performed by UE 210. In someimplementations, one or more process blocks of FIG. 5 may be performedby another device or a group of devices separate from or including UE210, such as base station 220, MME 230, and provisioning device 240.

As shown in FIG. 5, process 500 may include determining whether roamingcoverage, LTE coverage, and/or sufficient LTE coverage is present (block510). For example, UE 210 may determine whether roaming coverage, LTEcoverage, and/or sufficient LTE coverage is available (e.g., bymonitoring a strength of a wireless signal received by UE 210 and/or atype of coverage available). In some implementations, when determiningwhether sufficient LTE coverage is available, UE 210 may determinewhether a signal strength associated with the LTE coverage satisfies athreshold signal strength. If UE 210 determines that roaming coverage,LTE coverage, and/or sufficient LTE coverage is present, then process500 may include returning back to block 510 (block 510—YES).

As further shown in FIG. 5, if UE 210 determines that roaming coverage,LTE coverage, and/or sufficient LTE coverage is not present, thenprocess 500 may include enabling LTE category M1 extended coverage mode(block 520). For example, UE 210 may enable LTE category M1 extendedcoverage mode. In some implementations, when enabling LTE category M1extended coverage mode, UE 210 may configure a setting and/or aparameter of UE 210 to enable UE 210 to operate according to LTEcategory M1 extended coverage mode. In some implementations, whenenabling LTE category M1 extended coverage mode, UE 210 may enable UE210 to operate according to a lower LTE category than the LTE categoryat which UE 210 is currently operating, at which UE 210 operates bydefault, or the like.

As further shown in FIG. 5, process 500 may include configuring a modemto LTE category M1 mode (block 530). For example, UE 210 may configure amodem of UE 210 to LTE category M1 mode to cause, or enable, the modemto operate according to LTE category M1. In some implementations, whenconfiguring a modem to LTE category M1, UE 210 may configure a settingand/or a parameter of the modem to enable the modem to operate accordingto LTE category M1. Additionally, or alternatively, configuring themodem may cause, or enable, UE 210 to operate according to LTE categoryM1.

As further shown in FIG. 5, process 500 may include configuring an RFparameter for LTE category M1 mode (block 540). For example, UE 210 mayconfigure an RF parameter for LTE category M1 mode to enable UE 210 tooperate according to LTE category M1. In some implementations,configuring the RF parameter may enable UE 210 to communicate whensignal strength of a wireless signal does not satisfy a threshold orwhen a particular type of coverage is not available (e.g., roamingcoverage or LTE coverage), thereby improving communications of UE 210.

As shown in FIG. 5, process 500 may include configuring a voice clientto decrease delay sensitivity (block 550). For example, UE 210 mayconfigure a voice client of UE 210 to decrease delay sensitivity of thevoice client, while maintaining a particular quality of service thatallows for intelligible calls. In some implementations, when configuringa voice client, UE 210 may configure a setting and/or a parameter of thevoice client. In some implementations, configuring the voice client mayenable UE 210 to communicate when signal strength of a wireless signaldoes not satisfy a threshold or when a particular type of coverage isnot available, thereby improving communications of UE 210.

As further shown in FIG. 5, process 500 may include attaching to thenetwork in LTE category M1 mode and enabling coverage enhancement (block560). For example, UE 210 may attach to network 250 in LTE category M1mode and enable coverage enhancement. In some implementations, whenattaching to network 250, UE 210 may send an attach request to MME 230.Additionally, or alternatively, UE 210 may send a request toprovisioning device 240, such as to cause provisioning device 240 todetermine whether UE 210 is permitted to operate according to LTEcategory M1 (e.g., to determine whether a user account associated withUE 210 has a subscription for LTE category M1 services). In someimplementations, when enabling coverage enhancement, UE 210 mayconfigure a setting or a parameter of UE 210, such as to cause UE 210 torepeat transmissions of communications and/or to frequency hop. Thisenables UE 210 to communicate when signal strength of a wireless signaldoes not satisfy a threshold, thereby improving communications of UE210.

As further shown in FIG. 5, process 500 may include monitoring a signalstrength of the roaming coverage and/or the LTE coverage (block 570).For example, UE 210 may monitor the signal strength of a wireless signalassociated with the roaming coverage and/or the LTE coverage. In someimplementations, UE 210 may monitor the signal strength by measuring thesignal strength (e.g., dBms) periodically, according to a schedule,based on input of a user of UE 210, or the like.

As further shown in FIG. 5, process 500 may include determining whetherthe signal strength is sufficient (block 580). For example, UE 210 maydetermine whether the signal strength is sufficient for normal operationof UE 210. In some implementations, UE 210 may determine whether thesignal strength is sufficient by comparing the signal strength to athreshold signal strength, a default signal strength, or the like. Ifthe signal strength is not sufficient for normal operation, then process500 may include returning to block 570. For example, UE 210 may continueto monitor the signal strength of a wireless signal associated with theroaming coverage and/or the LTE coverage.

As further shown in FIG. 5, if the signal strength is sufficient fornormal operation, then process 500 may include reconfiguring UE 210, themodem, the voice client, and/or the RF parameters (block 590). Forexample, if the signal strength satisfies a threshold signal strength,then UE 210 may reconfigure UE 210, the modem, the voice client, and/orthe RF parameters to operate according to a default LTE category, a userspecified LTE category, an LTE category higher than LTE category M1(e.g., LTE category 2 or LTE category 4), or the like. In someimplementations, when LTE 210 reconfigures, UE 210 may monitor a signalstrength of a wireless signal, determine whether a particular type ofcoverage is available, and/or determine whether the coverage issufficient. In other words, process 500 may include returning to block510 and/or block 580.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is an example process 600 relating to the example process shownin FIG. 4. Specifically, FIG. 6 shows an example process for extendingcharge duration of UE 210. In some implementations, one or more processblocks of FIG. 6 may be performed by UE 210. In some implementations,one or more process blocks of FIG. 6 may be performed by another deviceor a group of devices separate from or including UE 210, such as basestation 220, MME 230, and provisioning device 240.

As shown in FIG. 6, process 600 may include determining whether a chargelevel of a battery is below a percentage (block 610). For example, UE210 may determine whether a charge level of a battery of UE 210 is belowthree percent (3%), 60 percent (60%), or some other percentage of thebattery's total charge capacity. In some implementations, the percentagemay include a default percentage, a percentage configured by a user ofUE 210, or the like.

As further shown in FIG. 6, if UE 210 determines that the charge levelof the battery is not below the percentage, then process 600 may includereturning to block 610 (block 610-NO). For example, if the charge levelof the battery is greater than 3%, then process 600 may includecontinuing to determine whether the charge level is below thepercentage.

As further shown in FIG. 6, if the charge level of the battery is belowthe percentage (block 610—YES), then process 600 may include determiningwhether a user of the UE accepts a battery saving mode (block 620). Forexample, if the charge level of the battery is below 3%, then UE 210 mayprovide, for display, a notification indicating the charge level anddetermining whether a user of UE 210 wants UE 210 to operate accordingto LTE category M1 battery saving mode (e.g., based on input of theuser).

As further shown in FIG. 6, if the user does not accept the batterysaving mode (block 620-NO), then process 600 may include continuingnormal operation (block 630). For example, if the user does not acceptthe battery saving mode, then UE 210 may operate without configuring asetting or a parameter of UE 210. As another example, UE 210 maycontinue to operate in LTE power saving mode, different from a batterysaving mode, until the battery of UE 210 is depleted of a charge.

As further shown in FIG. 6, if the user accepts the battery saving mode(block 620—YES), then process 600 may include enabling an LTE categoryM1 battery saving mode (block 640). For example, if the user accepts thebattery saving mode, then UE 210 may enable the LTE category M1 batterysaving mode. In some implementations, UE 210 may configure a settingand/or a parameter of UE 210 when enabling the LTE category M1 batterysaving mode, such as by limiting voice data or SMS data to optimizeduration of the charge of the battery.

As further shown in FIG. 6, process 600 may include determining whetherthe battery is charging (block 650). For example, UE 210 may determinewhether the battery is charging while in LTE category M1 battery savingmode. In some implementations, UE 210 may determine whether UE 210 isreceiving a charge or is connected to a power source other than thebattery of UE 210 when determining whether the battery is charging.

As further shown in FIG. 6, if the battery is not charging (block650-NO), then process 600 may include returning to block 640. Forexample, if the battery is not charging, then UE 210 may continue tooperate in LTE category M1 battery saving mode.

As further shown in FIG. 6, if the battery is charging (block 650—YES),then process 600 may include reconfiguring to disable the LTE categoryM1 battery saving mode (block 660). For example, if the battery ischarging, then UE 210 may reconfigure UE 210 to disable the LTE categoryM1 battery saving mode. For example, UE 210 may reconfigure a settingand/or a parameter of UE 210 to a default configuration and/or auser-defined configuration to disable the LTE category M1 battery savingmode.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIG. 7 is a call flow diagram of an example implementation 700 relatingto the example process shown in FIG. 4. Specifically, FIG. 7 shows anexample implementation of a successful validation of UE 210. Exampleimplementation 700 includes UE 210, base station 220, MME 230, andprovisioning device 240.

As shown in FIG. 7, and by reference number 705, UE 210 may have asignal strength and/or a charge level that satisfy a threshold. In someimplementations, UE 210 may determine that UE 210 has a signal strengthand/or a charge level that satisfy a threshold by detecting, andcomparing to a threshold, the signal strength and/or the charge level.As shown by reference number 710, UE 210 may transmit a detach requestmessage to base station 220. For example, UE 210 may transmit the detachrequest based on determining that UE 210 has a signal strength and/or acharge level that satisfy a threshold. As shown by reference number 715,base station 220 may transmit the detach request message, from UE 210,to MME 230. As shown by reference number 720, MME 230 may process thedetach request and cause UE 210 to detach (e.g., from network 250).

As shown by reference number 725, UE 210 may request attachment (e.g.,to network 250) in LTE category M1 coverage enhancement mode or batterysaving mode, such as by sending an attach request message. As shown byreference number 730, UE 210 may transmit an attach request message tobase station 220. In some implementations, the attach request messagemay include a request to attach to network 250 in LTE category M1coverage enhancement mode or battery saving mode.

As shown by reference number 735, base station 220 may transmit theattach request message to MME 230. As shown by reference number 740, MME230 may send a request to validate a subscription associated with UE 210to determine whether to permit UE 210 to attach in LTE category M1coverage extension mode or battery saving mode. As shown by referencenumber 745, provisioning device 240 may validate the subscriptionassociated with UE 210 and accept the request for UE 210 to attach inLTE category M1 coverage extension mode or battery saving mode.

As shown by reference number 750, provisioning device 240 may transmit asubscription valid message to MME 230 to indicate that the subscriptionassociated with UE 210 has been validated. As shown by reference number755, MME 230 may transmit an attach accept message to base station 220(e.g., based on provisioning device 240 validating the subscriptionassociated with UE 210). As shown by reference number 760, base station220 may transmit the attach accept message to UE 210. As shown byreference number 765, UE 210 may operate in LTE category M1 coverageextension mode or battery saving mode until a signal strength and/or acharge level satisfy another threshold.

As indicated above, FIG. 7 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 7.

FIG. 8 is a call flow diagram of an example implementation 800 relatingto the example process shown in FIG. 4. Specifically, FIG. 8 shows anexample implementation of an unsuccessful validation of UE 210. Exampleimplementation 800 includes UE 210, base station 220, MME 230, andprovisioning device 240.

As shown in FIG. 8, and by reference number 805, UE 210 may have asignal strength and/or a charge level that satisfy a threshold. As shownby reference number 810, UE 210 may transmit a detach request message tobase station 220. For example, UE 210 may send the detach request basedon determining that UE 210 has a signal strength and/or a charge levelthat satisfy a threshold. As shown by reference number 815, base station220 may transmit the detach request message to MME 230. As shown byreference number 820, MME 230 may process the detach request and causeUE 210 to detach (e.g., from network 250).

As shown by reference number 825, LTE 210 may request attachment in LTEcategory M1 coverage extension mode or battery saving mode, such as bysending an attach request message. As shown by reference number 830, UE210 may transmit the attach request message to base station 220. In someimplementations, the attach request message may include a request toattach to network 250 in LTE category M1 coverage extension mode orbattery saving mode.

As shown by reference number 835, base station 220 may transmit theattach request message to MME 230. As shown by reference number 840, MME230 may request provisioning device 240 to validate a subscription of UE210 to determine whether to permit UE 210 to attach in LTE category M1coverage extension mode or battery saving mode (e.g., based onprocessing the attach request message from UE 210). As shown byreference number 845, provisioning device 240 may fail to validate thesubscription associated with UE 210 and may reject the request for UE210 to attach in LTE category M1 coverage extension mode or batterysaving mode.

As shown by reference number 850, provisioning device 240 may transmit asubscription invalid message to MME 230 to indicate that provisioningdevice 240 did not validate the subscription associated with UE 210. Forexample, MME 230 may transmit a message that includes an identifierindicating that the request was rejected due to an invalid subscription.As shown by reference number 855, MME 230 may transmit an attach rejectmessage to base station 220 (e.g., based on provisioning device 240failing to validate the subscription). As shown by reference number 860,base station 220 may transmit the attach reject message from MME 230 toUE 210. As shown by reference number 865, UE 210 may configure to adefault configuration (e.g., a default or user-defined set of settingsand/or parameters of UE 210) and may reattempt to attach to network 250.

As indicated above, FIG. 8 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 8.

Implementations described herein enable a UE to configure a setting or aparameter of the UE to operate according to a particular UE category,such as a lower UE category than the UE category at which the UE iscurrently operating or a UE category associated with a different type ofdevice than the UE. In this way, communications of a UE may be improvedby permitting the UE to communicate when a signal strength of a wirelesssignal would otherwise prevent, or disrupt, the UE from communicating.Additionally, or alternatively, battery and/or power resources of the UEmay be conserved by modifying one or more particular functionalities ofthe UE that consume significant battery and/or power resources. Thisenables extension of duration of a battery of the UE, thereby improvingperformance of the UE.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

1. A device, comprising: a memory; and one or more processors to:receive signal information associated with a wireless signal or chargeinformation associated with a charge level, the signal informationindicating a signal strength of the wireless signal, the chargeinformation indicating the charge level of a battery of the device;identify a threshold based on call information regarding a callassociated with the signal information; determine whether the signalstrength or the charge level satisfies the threshold; configure aparameter or a setting of the device to cause the device to operateaccording to a long term evolution (LTE) category based on determiningwhether the signal strength or the charge level satisfies the threshold,the LTE category being different from a default LTE category of thedevice, the LTE category defining a third generation partnership project(3GPP) combined uplink and downlink capability specification; and attachto a network in association with configuring the parameter or thesetting to cause the device to operate according to the LTE category. 2.The device of claim 1, where the one or more processors are further to:monitor the signal strength information or the charge information;re-determine whether the signal strength or the charge level satisfiesthe threshold; and reconfigure the parameter or the setting to cause thedevice to operate according to a different LTE category based ondetermining that the signal strength or the charge level satisfies thethreshold.
 3. The device of claim 1, where the one or more processors,when configuring the parameter or the setting, are to: configure thedevice to operate according to a lower LTE category than the default LTEcategory of the device.
 4. The device of claim 1, where the one or moreprocessors are further to: request attachment to the network based onconfiguring to operate according to the LTE category, the LTE categorybeing LTE category M1; receive information indicating whether the deviceis associated with a subscription that permits the device to operateaccording to the LTE category; and where the one or more processors,when attaching to the network, are to: attach to the network in LTEcategory M1 coverage enhancement mode based on the informationindicating that the device is associated with the subscription thatpermits the device to operate according to the LTE category.
 5. Thedevice of claim 1, where the one or more processors, when configuringthe parameter or the setting, are to: configure the parameter or thesetting to cause the device to operate according to a first LTE categorybased on the signal strength or the charge level satisfying thethreshold, or configure the parameter or the setting to cause the deviceto operate according to a second LTE category based on the signalstrength or the charge level satisfying another threshold.
 6. The deviceof claim 1, where the one or more processors are further to: negotiateone or more settings related to coverage enhancement or charge duration;and where the one or more processors, when attaching to the network, areto: attach to the network in association with negotiating the one ormore settings related to coverage enhancement or charge duration.
 7. Thedevice of claim 1, where the one or more processors are further to:configure the 3GPP combined uplink and downlink capabilityspecification, the 3GPP combined uplink and downlink capabilityincluding at least one of: an uplink shared channel (UL-SCH)specification associated with the LTE category, a downlink sharedchannel (DL-SCH) specification associated with the LTE category, or atransmission time interval (TTI) specification associated with the LTEcategory; and where the one or more processors, when attaching to thenetwork, are to: attach to the network based on configuring the 3GPPcombined uplink and downlink capability specification.
 8. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors, cause the one or more processors to: receivesignal information that indicates a signal strength of a wireless signalreceived by a user equipment; identify a threshold signal strength basedon call information regarding a call associated with the signalinformation; compare the signal information to information indicatingthe threshold signal strength; determine whether the signal strengthsatisfies the threshold signal strength based on comparing the signalinformation and the information indicating the threshold signalstrength; configure the user equipment to operate according to a devicecategory based on determining whether the signal strength satisfies thethreshold signal strength, the device category being associated with asetting or a parameter related to communications of the user equipment,the device category being associated with an uplink and downlinkcapability specification; and request to attach to a network based onconfiguring the user equipment to operate according to the devicecategory.
 9. The non-transitory computer-readable medium of claim 8,where the one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: monitor anamount of signal power being received by the user equipment to determinewhether the signal strength satisfies the threshold signal strength;determine that the amount of signal power being received by the userequipment satisfies the threshold signal strength; and configure theuser equipment to operate according to a different device category basedon determining that the amount of signal power being received by theuser equipment satisfies the threshold signal strength.
 10. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions, when executed by the one or more processors, furthercause the one or more processors to: receive an indication that arequest to attach to the network is denied; reconfigure the userequipment to operate according to a different device category, thedifferent device category being a higher device category than the devicecategory; and re-request to attach to the network based on reconfiguringthe user equipment.
 11. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions, that cause the one or moreprocessors to configure the user equipment, cause the one or moreprocessors to: configure a modem of the user equipment to operateaccording to the device category.
 12. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,that cause the one or more processors to configure the user equipment,cause the one or more processors to: configure a radio frequency (RF)parameter of the user equipment to cause the user equipment to operateaccording to the device category.
 13. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,that cause the one or more processors to configure the user equipment,cause the one or more processors to: configure a voice client of theuser equipment to cause the user equipment to operate according to thedevice category.
 14. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions, when executed by the one ormore processors, further cause the one or more processors to: determinewhether roaming coverage is available; and where the one or moreinstructions, that cause the one or more processors to configure theuser equipment to operate according to the device category, cause theone or more processors to: configure the user equipment to operateaccording to the device category based on determining that roamingcoverage is not available. 15.-20. (canceled)
 21. A method, comprising:receiving, by a device, signal information associated with a wirelesssignal, the signal information indicating a signal strength of thewireless signal; identifying, by the device, a threshold based on callinformation regarding a call associated with the signal information;determining, by the device, whether the signal strength satisfies thethreshold; configuring, by the device, a parameter or a setting of thedevice to cause the device to operate according to a long term evolution(LTE) category based on determining whether the signal strengthsatisfies the threshold, the LTE category being different from a defaultLTE category of the device; and attaching, by the device, to a networkin association with configuring the parameter or the setting to causethe device to operate according to the LTE category.
 22. The method ofclaim 21, further comprising: monitoring the signal strengthinformation; re-determining whether the signal strength satisfies thethreshold; and reconfiguring the parameter or the setting to cause thedevice to operate according to a different LTE category based ondetermining that the signal strength satisfies the threshold.
 23. Themethod of claim 21, further comprising: requesting attachment to thenetwork based on configuring to operate according to the LTE category,the LTE category being LTE category M1; receiving information indicatingwhether the device is associated with a subscription that permits thedevice to operate according to the LTE category; and where attaching tothe network comprises: attaching to the network in LTE category M1coverage enhancement mode based on the information indicating that thedevice is associated with the subscription that permits the device tooperate according to the LTE category.
 24. The method of claim 21, whereidentifying the threshold based on call information regarding the callassociated with the signal information comprises: determining whetherthe threshold is a first threshold or second threshold, the firstthreshold being associated with a first quality of service and thesecond threshold being associated with a second quality of service. 25.The method of claim 21, further comprising: negotiating one or moresettings related to coverage enhancement or charge duration; and whereattaching to the network comprises: attaching to the network inassociation with negotiating the one or more settings related tocoverage enhancement.
 26. The method of claim 21, where the LTE categorydefining a third generation partnership project (3GPP) combined uplinkand downlink capability specification; and further comprising:configuring the 3GPP combined uplink and downlink capabilityspecification, the 3GPP combined uplink and downlink capabilityincluding at least one of: an uplink shared channel (UL-SCH)specification associated with the LTE category, a downlink sharedchannel (DL-SCH) specification associated with the LTE category, or atransmission time interval (TTI) specification associated with the LTEcategory; and where attaching to the network comprises: attaching to thenetwork based on configuring the 3GPP combined uplink and downlinkcapability specification.